Skip to content

docs: weekly changelog update - #252

Merged
yash-pouranik merged 4 commits into
mainfrom
changelog/week-of-26782331923
Jun 1, 2026
Merged

docs: weekly changelog update#252
yash-pouranik merged 4 commits into
mainfrom
changelog/week-of-26782331923

Conversation

@yash-pouranik

@yash-pouranik yash-pouranik commented Jun 1, 2026

Copy link
Copy Markdown
Member

Auto-generated weekly changelog entry. Please review before merging.

Summary by CodeRabbit

  • Documentation
    • Updated changelog for June 2026 documenting deliverables and user-facing impacts: queue-based asynchronous database exports for more reliable/robust exports; soft-delete recovery to restore recently removed items; streamlined onboarding and environment configuration; webhook dispatch offloading to improve responsiveness; stricter cookie SameSite enforcement for improved session security; and OAuth timeout handling improvements for more predictable sign-in behavior.

@coderabbitai

coderabbitai Bot commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Warning

Review limit reached

@yash-pouranik, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 32 minutes and 55 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a1f05db5-a817-4124-b376-b2e593ff9c12

📥 Commits

Reviewing files that changed from the base of the PR and between bd72d81 and eef86ab.

📒 Files selected for processing (1)
  • mintlify/docs/changelog/june-2026.mdx
📝 Walkthrough

Walkthrough

This PR adds a June 2026 changelog entry to the documentation. The new MDX file contains frontmatter metadata and an update section documenting product features, improvements, and security fixes for the week ending 2026-06-01.

Changes

June 2026 Changelog Entry

Layer / File(s) Summary
Changelog frontmatter and update content
mintlify/docs/changelog/june-2026.mdx
Introduces a new changelog entry with title and description metadata, followed by an Update section documenting features (queue-based async DB export, soft-delete recovery), improvements (onboarding/.env updates, webhook dispatch offloading), and security items (cookie SameSite enforcement, OAuth timeout handling).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A changelog hops into June's bright glow,
New features and fixes help projects grow,
Queue exports queued, soft-deletes restored,
Env and webhooks tuned, security onboard,
Notes penned in MDX so the team can know.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'docs: weekly changelog update' is vague and generic, using non-descriptive terms that don't convey meaningful information about the specific changeset. Consider using a more specific title that reflects the actual content, such as 'docs: add June 2026 changelog with async export and security updates' to better communicate the changes.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch changelog/week-of-26782331923

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@mintlify

mintlify Bot commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
urbackend 🟢 Ready View Preview Jun 1, 2026, 9:12 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds the first June 2026 Mintlify changelog entry documenting the week of 2026-05-25–2026-06-01 for urBackend.

Changes:

  • Adds a new <Update> block for 2026-06-01 with “New features”, “Improvements”, and “Bug fixes”.
  • Documents multiple platform/UI updates and several PR-linked fixes.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread mintlify/docs/changelog/june-2026.mdx Outdated
Comment thread mintlify/docs/changelog/june-2026.mdx Outdated
Comment thread mintlify/docs/changelog/june-2026.mdx Outdated
Comment thread mintlify/docs/changelog/june-2026.mdx Outdated

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@mintlify/docs/changelog/june-2026.mdx`:
- Around line 17-20: Update the changelog lines to format filenames and code
references with backticks: wrap .editorconfig, bullmq, .env.example, husky, and
lint-staged in code formatting in the entries for "Standardized formatting",
"Offload sync webhook dispatch", "Onboarding improvements", and "Husky and
lint-staged pre-commit hook" so the file names and tool names appear as inline
code (e.g., `.editorconfig`, `bullmq`, `.env.example`, `husky`, `lint-staged`)
throughout the section.
- Around line 11-13: The two changelog lines "Back to Home button on signup
page" and "Home button on signup page" are ambiguous duplicates; consolidate or
differentiate them by either merging into a single entry (e.g., "Add Home/Back
to Home button on signup page for easier navigation") or clarifying distinct
behavior (e.g., rename one to "Home button on signup page — navigates to root"
and the other to "Back to Home button on signup page — returns to previous home
state"), and ensure the remaining "Back to Top button" line stays separate and
clearly describes its behavior; update the text in the changelog accordingly to
remove overlap.
- Around line 9-20: Rewrite each changelog bullet to use second-person active
voice and a single concise idea per line; replace generic imperatives like
"Implement/Add/Improve" with "You can now…" or "You" phrasing and split any
headline+explanation into separate concise bullets. Update the feature bullets
such as "Queue-based async DB export pipeline", "Soft-delete recovery", "Back to
Home button on signup page", "Back to Top button", and "Home button on signup
page" to read like "You can now…" statements and ensure they are one idea each,
and likewise tighten the "Improvements" bullets (e.g., ".editorconfig", "Offload
sync webhook dispatch", "Onboarding improvements", "Husky and lint-staged
pre-commit hook") into short second-person lines that state the benefit or
action plainly.
🪄 Autofix (Beta)

❌ Autofix failed (check again to retry)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2b62cdeb-c812-41a7-b7ae-9e44dd522518

📥 Commits

Reviewing files that changed from the base of the PR and between 0a23a04 and d2e7477.

📒 Files selected for processing (1)
  • mintlify/docs/changelog/june-2026.mdx

Comment thread mintlify/docs/changelog/june-2026.mdx Outdated
Comment thread mintlify/docs/changelog/june-2026.mdx Outdated
Comment thread mintlify/docs/changelog/june-2026.mdx Outdated
@mintlify

mintlify Bot commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Rewrote changelog bullets in second-person active voice, consolidated duplicate Home button entries, and wrapped file/tool names in backticks.

@yash-pouranik

Copy link
Copy Markdown
Member Author

@coderabbitai
I feel the changelog is good
but the UI structure is not good

@coderabbitai

coderabbitai Bot commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Tip

For best results, initiate chat on the files or code changes.

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
fd "june-2026.mdx" --exec cat {}

Length of output: 1443



@yash-pouranik Thanks for the feedback! Here are the two main structural issues I see and how to fix them:


Problem 1 — All categories crammed into one <Update> block

Mintlify's <Update> component is designed to be used one per category so each gets its own colored tag badge and visual separation in the rendered UI. Right now everything is in a single block with four tags stacked on it.

Problem 2 — "Security" tag has no dedicated section

The tags array includes "Security", but security-related fixes (#240, #220, #224, #221) are buried inside Bug Fixes with no visual distinction.


Suggested structure

---
title: Changelog
description: What's new in urBackend — new features, improvements, and fixes.
---

<Update label="2026-06-01" description="Week of 2026-05-25–2026-06-01" tags={["Feature"]}>
  ## New Features

  - Export databases asynchronously through a queue-based pipeline for improved performance.
  - Recover soft-deleted records for better data management.
  - Return to the home page from the signup page via the new **Home** button.
  - Jump to the top of long pages via the new **Back to Top** button.
</Update>

<Update label="2026-06-01" description="Week of 2026-05-25–2026-06-01" tags={["Improvement"]}>
  ## Improvements

  - Standardized formatting across editors via `.editorconfig`.
  - Faster sync webhook dispatch, now offloaded to `bullmq`.
  - Cleaner onboarding experience with an updated `.env.example` and added source comments.
  - Improved code quality via `husky` and `lint-staged` pre-commit hooks.
</Update>

<Update label="2026-06-01" description="Week of 2026-05-25–2026-06-01" tags={["Fix"]}>
  ## Bug Fixes

  - Fix dashboard get data query engine (`#230`)
  - Fix query engine limit fields mock (`#231`)
  - Pin root dependency versions (`#236`)
</Update>

<Update label="2026-06-01" description="Week of 2026-05-25–2026-06-01" tags={["Security"]}>
  ## Security

  - Enforce `SameSite=Lax` on all cookies to prevent CSRF attacks (`#240`)
  - Add timeout handling for OAuth fetch requests (`#220`)
  - Patch storage quota evasion loophole in update pipeline (`#224`)
  - Add missing max-length constraints to auth schemas (`#221`)
</Update>

Bonus — voice inconsistency

The current file mixes styles: Features use "You can now…" while Improvements use "You now get…" / "You benefit from…" / "You get…". The suggested version above normalises everything to a plain imperative/descriptive style, which is shorter and more consistent across sections.

Would you like me to plan the code change for you?

(´・ω・`) 🐇

@yash-pouranik

Copy link
Copy Markdown
Member Author

@mintlify

@coderabbitai

coderabbitai Bot commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Note

Autofix is a beta feature. Expect some limitations and changes as we gather feedback and continue to improve it.

Autofix skipped. No unresolved CodeRabbit review comments with fix instructions found.

@yash-pouranik
yash-pouranik temporarily deployed to changelog/week-of-26782331923 - urBackend-frankfrut PR #252 June 1, 2026 21:38 — with Render Destroyed
@yash-pouranik
yash-pouranik merged commit 5d34cf8 into main Jun 1, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants